home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
029a
/
scc.zip
/
SAMPLE.V1
< prev
next >
Wrap
Text File
|
1991-09-11
|
10KB
|
238 lines
The above SCC Log (along with different SCC Log option settings)
can help generate a "filtered" SCC change control report Log to
what is important (delete or insert status) and not important
(blank status) in your file.
For example you may not want the '-' or '+' (delete or insert)
Log status characters for such lines containing differences of
only "White Space", "Upper/Lower Case" etc.
At any time you may press the
F1 key for the help menu.
F2 key for the QUICK help menu.
START OF EXAMPLES.....
" Deleted Lines "
Will show what line and line # that was deleted from the Old.
" Common Lines "
Common Line numbers between the Old and New documents. Cursor
status will show the corresponding Old line #.
" Moved Lines "
These are exact matching lines between documents but may have
different line numbers.
" Ignore W h i t e Sp "
All the text match e xcept for white space between documents.
" IGNORE CASE "
All The Text Match Except For UPPER/lower Case between documents.
" MULTI 123 MATCH "
All the TEXT match by using Two 2 or more options between the Old
and New documents. For example if the option "IGNORE CASE" and
"IGNORE NUMBERS" allowed the 123 lines match t h e n this status.
" Ignore Numbers "
654321 All the text match except for numbers between documents.
Strip End White
If "Strip End White" was selected the following lines will be
exactly alike (same length) and would show as "Common Lines".
If "Strip End White" was ** NOT ** selected then the lines
will be of different lengths.
Common lines
These lines are common between the Old and New documents.
** Note ** SCC can also track and VIEW any (ASCII TEXT)
formatted document such as the following.
Page 1 Overview.scc
Software Change Control (SCC)
Softtime Systems
P.O. Box 2447
Lk Ronknnkoma LI. NY 11779
516 981-8386
Copyright (c) 1990-91 by Walter Erickson
All Rights Reserved.
"A small CASE for a big problem"
Page 1
OVERVIEW
Questions "about" SCC
What is SCC .
Software Change Control SCC, as the name implies, is one of the most
powerful an cost-effective tool in this energing field of CASE.
SCC features friendly menu-driven interfaces (with automatic context help)
suitable for use by non-technical administrative, as well as for the
sophisticated user.
SCC closely tracks (logs) all software/text changes between two similar
source files, thereby giving a complete (version to version) audit trail.
A SCC generated Log greatly simplifies any user request for the
(identification) of what, when and why changes were made.
What does CSS do ?
------------------
When SCC is run the tracking (output) log file will then reflect
(context) what changes have occurred between the two source files,
thus allowing the programmer and/or management to have a clear visual SCC
log of all software and/or text changes.
This feature enables the user to control all enhancements and
documentation of source data at this critical level.
Why is SCC needed ?
-------------------
All software source files will need changes. In fact, it is a truism that
every software project released, including those released quite recently,
need changes. The most important consideration at this stage is to regulate
and control the documentation and its changes.
SCC is a decomposition process that offers a complete and precise
description of what (line-by-line) changes have occurred between two source
files. This results in faster development time, along with software that is
far less likely to fail in use.
Page 3
Can managers use SCC ?
----------------------
Using SCC creates an environment that is very time and cost effective.
SCC allows changes to be made in a more maintainable, reliable and
controllable way; that is, software control is fully documented, along with
a full audit trail of what changes have occurred between software versions.
The management of software changes at the programming (source) level
(generally accepted as the most expensive and weakest link in software
management) is one of the most difficult problems managers and programmers
alike have.
SCC greatly improves the suitability and appropriateness of software
change documents; enhances clarity, readability, reliability and complete
recoverability; allowing software changes to be a great deal easier to
track and maintain.
Does SCC require a speceal editor ?
-----------------------------------
No, all that's required is that the input source files to CSS be in
(Ascii TEXT) format.
Does CSS Require a Data Base ?
------------------------------
No, SCC can either be integrated into a data base or stand alone, for
most small projects a data base is not necessary, thus eliminating
complexity and cost (KISS). All header file-id, code and documentation
changes "between versions" are kept within the SCC Log itself.
Can I run SCC against existing versions ?
-----------------------------------------
Yes, you can build new and complete SCC change logs from older existing
(version to version) files, this will give a entire audit trail of any
software changes between versions.
What can SCC be used for ?
--------------------------
o Documenting
o Software control
o Software Debugging
o version pre release (development) change control
o Code walkthrough's
o etc.
Using SCC for Documenting
-------------------------
When SCC is run, the tracking (output) log file will then reflect (in
context) what changes that have occurred between the two (input) source
files, thus allowing the programmer and/or management to control, enhance
and document software at this critical source level.
SCC generates a software change (log) that closely tracks and records all
changes consisting of a header, control change numbers and special symbols
to reflect the operations of delete '-', insert '+', move ' ' etc.
Page 3
Using SCC for Software control
------------------------------
The Manager/Programmer can visually see on one listing (the CHANGE Log)
all changes and special tracking symbols that were necessary to build the
later version from the earlier version, thus keeping an accurate control
over all changes.
SCC will also reveal all unintentional and possible unauthorized changes
to source files, thus preventing future problems in the next released
version.
SCC helps the programmer and manager to make changes, "edit out" any
tactical coding/design errors between two source files. This can be done by
using a similar method such as the following:
Initial Technical Design Review
o revision of raw draft coding design
o clarification of ambiguous design content
o identification of coding gaps and inconsistencies
o discovery of major/minor coding errors
Coding Review
o verification of content NOT already tested or debugged
o incorporation of late technical coding changes
o writing specs for changed docunentation
Final Technical Design Review
o refining the source code for usability
o minor "edit" cleanup
o careful configuration control and test proofing
Field Maintenance of Released Software
o discovery of unintentional coding errors
o discovery of undocumented features
o uncovering code that once worked, but now does not
o SCC Log header information for release identification and control
Page 5
SCC summary
-----------
SCC enables detailed verification of auditing accuracy, eliminates
undetected programming errors and drastically reduces manual desk checking
time.
The manager/programmer knows exactly what the changes are between
versions.
SCC accepts (ASCII TEXT) output from your favored editor.
SCC is a comprehensive utility designed to compare two files and generate
various reports (log files) that display any or all change differences as
they evolve.
You can track any coding progress on software changes by viewing an SCC
log against the previous and/or developing files.
You can backtrack to any previous version to examine what changes created
that release at that time.
SCC change log report (version to version) can greatly help in debugging
changes between versions (one works the other does not).
You can build new and complete SCC change logs from older existing
(version to version) files.
The key benefits of SCC are:
o lower project costs
o controlled release management
o structured walkthroughs
o faster software coding thruput
o higher software quality
If you would like further infomation about this or the SCC registered
programs, please call Walter Erickson at (516) 981-8386